@imbajin can we share the same COMMIT_ID with client-ci.yml (just use an global env var)

@imbajin can we share the same COMMIT_ID with client-ci.yml (just use an global env var)

I do want it too but not found the way to achieve it, however I get a better way to avoid hard code commit ID in ci

we could use "latestCommitID - X" (X >= 15 maybe) to get the stable code in server & no need update the ID by ourselves if not necessary (will submit a PR after this adaptor) #542

It is a method to use latestCommitID - X, but we can't control it freely. If we want to adapt to the latest code, we still need to change the X.
we may try reusable-workflow: https://docs.github.com/en/actions/using-workflows/reusing-workflows#using-inputs-and-secrets-in-a-reusable-workflow

It is a method to use latestCommitID - X, but we can't control it freely. If we want to adapt to the latest code, we still need to change the X. we may try reusable-workflow: docs.github.com/en/actions/using-workflows/reusing-workflows#using-inputs-and-secrets-in-a-reusable-workflow

Get it, but we can't set secrets/variables in settings, we lack the permission to set it 😢 (This is also the reason why in the early code, we could only write fixed commitID in multiple CI files)

BTW, we could create/submit a common action and publish it to github action repo & let other actions to extend it if github supports